Skip to content

chore: release main - #201

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

@launchdarkly/ai-claude-agents: 1.0.1

1.0.1 (2026-11-06)

@launchdarkly/ai-claude-messages: 1.0.0

1.0.0 (2026-11-06)

Features

  • add maxRetries to the messages handler factories (#165) (e2e7135)
@launchdarkly/ai-langchain-agents: 1.0.1

1.0.1 (2026-11-06)

@launchdarkly/ai-langchain-messages: 1.0.0

1.0.0 (2026-11-06)

Features

  • add maxRetries to the messages handler factories (#165) (e2e7135)
@launchdarkly/ai-litellm-agents: 1.0.1

1.0.1 (2026-11-06)

@launchdarkly/ai-litellm-messages: 1.0.0

1.0.0 (2026-11-06)

Features

  • add maxRetries to the messages handler factories (#165) (e2e7135)
@launchdarkly/ai-node: 1.0.1

1.0.1 (2026-11-06)

@launchdarkly/ai-openai-agents: 1.0.1

1.0.1 (2026-11-06)

@launchdarkly/ai-openai-messages: 1.0.0

1.0.0 (2026-11-06)

Features

  • add maxRetries to the messages handler factories (#165) (e2e7135)
@launchdarkly/ai-server: 1.0.0

1.0.0 (2026-11-06)

Experimental

  • shadow-requests: add experimental shadowConfig wrapper (#195) (4b08a98)

Features

  • add maxRetries to the messages handler factories (#165) (e2e7135)
  • evaluations: return tool errors to the model and mark eval spans for viewers (#203) (954fc69)

Bug Fixes

  • lifecycle: claim the in-flight init before a passed client's telemetry setup (#207) (054148c)
@launchdarkly/ai-typesafe: 1.0.1

1.0.1 (2026-11-06)

@launchdarkly/ai-vercel-agents: 1.0.1

1.0.1 (2026-11-06)

@launchdarkly/ai-vercel-messages: 1.0.0

1.0.0 (2026-11-06)

Features

  • add maxRetries to the messages handler factories (#165) (e2e7135)

This PR was generated with Release Please. See documentation.


Note

Overview
Release Please cut bumps every impacted package to the next patch (1.0.1 where needed), updates LD_AI_PACKAGE_VERSION exports, and syncs .release-please-manifest.json so downstream consumers know the new tags.

The regenerated changelogs document the @launchdarkly/ai-server work that already shipped: the experimental shadowConfig helper, maxRetries plumbing for all messages handler factories, evaluation telemetry tweaks that return tool errors to models, and the lifecycle fix that acquires the in-flight init mutex before telemetry wiring.

Reviewed by Cursor Bugbot for commit 948497d. Bugbot is set up for automated code reviews on this repo. Configure here.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 02567f0. Configure here.


### Features

* add maxRetries to the messages handler factories ([#165](https://github.com/launchdarkly/js-ai-sdk/issues/165)) ([e2e7135](https://github.com/launchdarkly/js-ai-sdk/commit/e2e7135ab1ec76986850856f140a3bacad38356d))

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Features pinned to published 1.0.0

High Severity

This release records maxRetries under a second 1.0.0 heading for @launchdarkly/ai-server and the *-messages packages. Those versions are already on npm, so the feature cannot publish and the compare range is empty.

Additional Locations (2)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 02567f0. Configure here.

@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 3 times, most recently from ce5ad5f to 823fe81 Compare November 6, 2026 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants